Skip to content

Conversation

@GajananCh
Copy link
Contributor

Updates all documentation to follow ISO GQL standard and best practices:

  • Replace CREATE keyword with INSERT (ISO GQL standard)
  • Use comma-separated patterns for multiple node insertions instead of separate statements (single atomic transaction vs multiple)
  • Add clarifying comments explaining single vs multiple node patterns
  • Remove unnecessary variable bindings when not used

Files updated:

  • Main README.md and all binding READMEs (Java, Python, SDK)
  • Documentation guides (Quick Start, Getting Started With GQL)
  • Add comprehensive JSON format test suite (json_format_tests.rs)
  • Add debug output to pattern_tests.rs for NEXT clause investigation

Technical rationale:

  • CREATE and INSERT are synonyms (parser.rs:3933-3936)
  • Comma-separated pattern is more efficient (1 transaction vs N)
  • Parser supports comma-separated syntax (parser.rs:3937)
  • Atomic all-or-nothing semantics

Updates all documentation to follow ISO GQL standard and best practices:

- Replace CREATE keyword with INSERT (ISO GQL standard)
- Use comma-separated patterns for multiple node insertions instead of
  separate statements (single atomic transaction vs multiple)
- Add clarifying comments explaining single vs multiple node patterns
- Remove unnecessary variable bindings when not used

Files updated:
- Main README.md and all binding READMEs (Java, Python, SDK)
- Documentation guides (Quick Start, Getting Started With GQL)
- Add comprehensive JSON format test suite (json_format_tests.rs)
- Add debug output to pattern_tests.rs for NEXT clause investigation

Technical rationale:
- CREATE and INSERT are synonyms (parser.rs:3933-3936)
- Comma-separated pattern is more efficient (1 transaction vs N)
- Parser supports comma-separated syntax (parser.rs:3937)
- Atomic all-or-nothing semantics
@GajananCh GajananCh requested a review from arvikar83 November 22, 2025 07:11
Copy link
Collaborator

@arvikar83 arvikar83 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approval Note:

Local CI tests may fail as a recent commit may have reintroduced Doc-Tests, although the same is currently skipped from the prod CI pipeline.

Approving thus, as prod CI is successful.

@GajananCh GajananCh merged commit eaeb61c into main Nov 24, 2025
8 checks passed
@GajananCh GajananCh deleted the docs_update2 branch November 24, 2025 17:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants